Release 10.1A: OpenEdge Getting Started:
Core Business Services

Audit security for OpenEdge databases

Each new database instance is created with a unique value (UUID) to clearly identify the database source of any audit table records. When a database is being moved or copied, the database administrator responsible can assign a new, unique identity to the new instance of the database. The generation of a new database identity preserves the point-of-access integrity in the audit data records. When each database instance has a unique identity, you can use the audit data to trace access to a particular instance and user.

Note that a read-only database copy can retain the original instance’s value, since it does not qualify as a unique database instance.

You cannot migrate pre-Release 10.0 OpenEdge databases to support auditing, and pre-Release 10.1A database clients cannot connect to an audit-enabled database. (A Release 10.0 database client can, of course, connect to a Release 10.1A database that does not have auditing enabled or has had auditing disabled and the data in all audit tables removed.)

For WebSpeed and AppServer-based applications, the application server must be updated to OpenEdge Release 10.1 before accessing an audit-enabled database.